bugfix: Fix schema meta-info serialization issue in HBaseRelation#94
Merged
yuanoOo merged 2 commits intooceanbase:mainfrom Jan 26, 2026
Merged
bugfix: Fix schema meta-info serialization issue in HBaseRelation#94yuanoOo merged 2 commits intooceanbase:mainfrom
yuanoOo merged 2 commits intooceanbase:mainfrom
Conversation
Problem: In a distributed Spark environment, the schema metadata (rowKey and columnFamilyMap) was stored in the HBaseRelation companion object. Since Scala companion objects (singleton/static variables) are not serialized and sent to executors, these variables were re-initialized to their default values (empty) on the executor side. This caused a java.lang.IllegalArgumentException: "" does not exist when flush() attempted to access the row key from the DataFrame schema using the empty field name. Fix: Refactored HBaseRelation to ensure proper serialization of schema metadata: Moved rowKey and columnFamilyMap from the companion object to immutable instance variables within the HBaseRelation class. Updated parseCatalog to return a tuple containing the StructType, rowKey, and columnFamilyMap. Updated the flush method to use these instance variables, ensuring that schema mapping information is correctly available on all executors.
davidzhangbj
approved these changes
Jan 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Problem: In a distributed Spark environment, the schema metadata (rowKey and columnFamilyMap) was stored in the HBaseRelation companion object. Since Scala companion objects (singleton/static variables) are not serialized and sent to executors, these variables were re-initialized to their default values (empty) on the executor side. This caused a java.lang.IllegalArgumentException: "" does not exist when flush() attempted to access the row key from the DataFrame schema using the empty field name.
Fix: Refactored HBaseRelation to ensure proper serialization of schema metadata:
Moved rowKey and columnFamilyMap from the companion object to immutable instance variables within the HBaseRelation class. Updated parseCatalog to return a tuple containing the StructType, rowKey, and columnFamilyMap. Updated the flush method to use these instance variables, ensuring that schema mapping information is correctly available on all executors.
fix #91
Solution Description